5. Coexistence for Management
Coexistence for management
includes managing mailboxes on Exchange Server 2003 and Exchange Server
2010, configuring and managing Exchange servers, and organization parameters and message tracking.
Numerous complexities are
involved in managing Exchange in a coexistence environment. This is why
the final goal of your Exchange Server 2010 upgrade should be to upgrade
to a native Exchange Server 2010 environment as soon as possible,
including decommissioning the Exchange Server 2003 computers. Lowering
the Total Cost of Ownership (TCO), including administration costs, is
usually a primary goal of the upgrade, and managing a mixed environment
presents many opportunities for human error. Managing multiple versions
of Exchange will add to your TCO, so it is recommended that you complete
your upgrade to Exchange Server 2010 as soon as possible, rather than
manage a coexistence environment for an extended period of time.
5.1. Managing Mailboxes
Exchange Server 2010 mailboxes are managed with Windows PowerShell via the EMS or the Exchange Management
Console (EMC), whereas Exchange Server 2003 mailboxes must be managed
using the Active Directory Users and Computers (ADUC) snap-in extension
for Exchange.
Note:
Important
Exchange Server 2010 mailboxes cannot be managed using the Exchange
Server 2003 tools. Exchange Server 2010 mailboxes modified in this
fashion will not be fully functional, although the Exchange Server 2003
tools do not actually block this from happening.
In
addition, the Exchange Server 2003 Move Mailbox Task Wizard can't be
used for any mailbox moves where the source or destination is Exchange
Server 2010. Mailbox moves between Exchange Server 2003 and Exchange
Server 2010 can be performed with the Exchange Server 2010 tools, with
Exchange Server 2003 as either source or destination. You can't create
mailboxes on Exchange Server 2003 using the Exchange Server 2010 tools,
although you can modify and remove Exchange Server 2003 mailboxes with
the Exchange Server 2010 tools; you must use the ADUC Exchange snap-in
to create Exchange Server 2003 mailboxes.
Apart from managing recipients, you need to be aware of several other issues when managing your Exchange organization in a coexistence environment with Exchange Server 2003.
5.2. Exchange Server 2003 Administrative Groups
The concept of
administrative groups was used in Exchange Server 2003 to allow for
administrative delegation of portions of the Exchange organization to
different administrators. Although this model provided a basic
delegation model, it was not as flexible as it could have been. For
example, after an Exchange Server 2003 computer was deployed into a
particular administrative group it could not be moved into a different
administrative group without removing and re-installing Exchange Server
2003.
As discussed in the Section 14.3.1.6
section of this chapter, when your Active Directory environment is
prepared for Exchange Server 2010, a new administrative group called Exchange Administrative Group (FYDIBOHF23SPDLT)
is created that holds all Exchange Server 2010 servers. This
administrative group is strictly for coexistence purposes; however, all
Exchange Server 2010 computers are installed in this administrative
group. Servers running Exchange Server 2010 cannot be moved from this
administrative group, and Exchange Server 2003 servers cannot be added
to it. In addition, this administrative group cannot be renamed.
In Exchange Server 2010,
administrative groups have been replaced with a Role-Based Access
Control (RBAC) delegation model that allows for much greater
granularity. Previously, the delegation model applied only to the
administrators who managed the Exchange infrastructure and recipients.
In Exchange Server 2010, however, RBAC controls not only administrative
tasks but also delegates to users the ability to administer their own
mailbox and distribution groups.
5.3. Managing Exchange Server, Database, and Organizational Settings
All organizational-level
settings must be managed with the Exchange Server 2010 administration
tools after Exchange Server 2010 has been introduced into the
environment. At a more granular level, Exchange Server 2010 computers
and mailboxes are managed with the Exchange Server 2010 management
tools, whereas Exchange Server 2003 computers must be administered
using the Exchange Server 2003 Exchange System Manager. In addition, as
mentioned in the Section 14.3.5.1
section of this chapter, Exchange Server 2003 mailboxes must be managed
using the Active Directory Users and Computers Exchange snap-in.
5.4. Message Tracking
You'll notice
significant differences in the message-tracking schemas and tools
between Exchange Server 2003 and Exchange Server 2010. This means that
messages sent and received by Exchange Server 2010 can only be tracked
with the Exchange Server 2010 management tools—Exchange Server 2010 does not have the Windows Management Instrumentation (WMI) support required by the Exchange Server 2003 Message
Tracking Center. In addition, the Exchange Server 2003 Message Tracking
Center cannot parse the Exchange Server 2010 message tracking logs.
Note:
A
message crossing both Exchange Server 2010 and Exchange Server 2003
must be tracked with a combination of the Exchange Server 2003 and
Exchange Server 2010 utilities; it can't be tracked with the same tools.
